
NB  If you are just installing the pre-built RPM only step 7 should be
    necessary.  If you are rebuilding the SRPM then steps 1 and 7 may
    be necessary.  Steps 2 through 6 should be taken care of by the RPM
    install.


Steps to build tmModule147Build.zip on RedHat Enterprise Linux 5 / CentOS 5

1. Make sure the following packages are installed (and their dependencies):
   gcc-c++
   httpd-devel
   apr-devel

   For example with "yum install <pkgnames>"

2. unzip tmModule147Build.zip then cd into

   tm_module_1_4_7/tm_module_1_4_7/linux_project_redhat 

3. run make

4. in the release subdirectory there should be a mod_tm.so file, copy
   that to /usr/lib/httpd/modules, make sure the permissions are ok
   (owner root:root, mode 755.)

5. The mod_tm module needs a "data" directory in ServerRoot, on RedHat
   this is in /etc/httpd.  As you don't normally want to write data into
   /etc the RedHat way of dealing with this would be to create an
   /etc/httpd/data symlink pointing to somewhere more appropriate,
   /var/www/data, for example.  So mkdir the "data" directory, set
   permissions, owner apache:apache and mode 750, and then create a
   symlink in /etc/httpd pointing there.

6. The normal RedHat way of accomodating module configuration needs is
   not to edit the main httpd.conf file directly but to drop a module-
   specific config file in /etc/httpd/conf.d, so put the included
   tm.conf file there.  Permissions should be root:root, mode 644.
   You may also want to disable other module config files if they
   may interfere with TM - any file ending  in ".conf" in that directory
   will be included in the apache configuration - so simply renaming a
   config file something.conf to something.conf.bak is enough to stop it
   being included.  (Better yet remove unnecessary modules from the system
   using rpm or yum.)

7. RedHat puts web pages in /var/www/html (so the content of the htdocs
   directory goes there.)

